Havish M Consulting
Customer Case Study · Quality Root Cause Assistant
Wires and Cables × Havish M Consulting

From a spark fault to its root cause, in minutes not weeks

On the cable manufacturer's insulation lines, the same defects kept coming back: pinholes, thin insulation, off-centre conductors. HMC built a root cause assistant for the quality team that joins rejection logs with line data, ranks the defects that cost most, scores every possible cause against evidence, and drafts the 8D report.

ClientWires and Cables FunctionQuality · Manufacturing ThemeRoot Cause Analysis & 8D
First-pass yield on insulation lines
0%
▲ from 94.1%
Spark faults per 100 km
0% fewer
▼ moisture and speed controls
Scrap cost on insulation lines
0% lower
▼ fewer cut-outs and rejected drums
Days to close a root cause analysis
0days
▼ from about 21 days

Figures indicative; validated metrics available on request.

The Challenge

Defects fixed, then back next month

Every insulation line produces thousands of kilometres of wire a month. A single pinhole means cutting out a length; thin insulation can scrap a whole coil.

Data in silos

Rejection registers, spark-tester counts and extruder settings lived in different sheets and logbooks.

Fixing the loudest, not the costliest

Teams chased the defect seen most recently, not the one costing the most metres and rupees.

Fishbones from memory

Cause lists were brainstormed in meetings; few causes were ever tested against data.

8D reports took weeks

Customer complaints waited around three weeks for a root cause and corrective action report.

HMC Approach

Join the data, then let it rank the causes

Built with the quality and production teams on the house wire and power cable insulation lines.

Select a step to see what happened.

Discover · Where the scrap really goes

Six months of rejection data walked through with QA and production.

  • Defect codes cleaned into one list.
  • Scrap valued in metres and rupees by product.
  • Line data available per run: speed, zone temperatures, compound lot, die hours.

Deliverable: Defect dictionary and data map.

Design · Causes you can test

Every fishbone cause written as a test on line data.

  • 6M cause library per defect (man, machine, method, material, measurement, environment).
  • Evidence score: how much more often the defect occurs when the cause is present.
  • 8D template agreed with the customer quality team.

Deliverable: Cause library and scoring rules.

Build · Monitor, Pareto, fishbone, 8D

One workflow from alarm to report.

  • Live line view with diameter, eccentricity and spark faults.
  • Auto Pareto and evidence-scored fishbone.
  • GenAI drafts the 8D from the data and the team's notes.

Deliverable: Root cause assistant.

Adopt · Daily quality huddle

The Pareto opens every morning meeting.

  • Top defect of the week gets an owner and an 8D.
  • Fixes verified on the control chart, not by feel.
  • Control plan and PFMEA updated when a root cause is confirmed.

Deliverable: Huddle routine and results on two lines.

Scale · Every line, every plant

Same cause library, local data.

  • Sheathing, cabling and wire drawing lines added.
  • Supplier quality gets lot-level feedback.
  • Customer complaints answered with an 8D in days.

Deliverable: Roll-out plan.

The Solution

Run a root cause analysis yourself

Thirty days of synthetic data from four lines. Inject a fault on the live line, find the costliest defect on the Pareto, see which causes the data supports, and get the 8D report.

✦ Write the 8D with GenAI

Optional. Without a key, the 8D and 5 Whys come from the cause library and the data. Add your OpenAI key to write the 8D from your own shop-floor notes and to classify a photo of a defect.

Templates
Your key goes only from this browser to OpenAI.
01 · Live line monitor

Insulation line EXT-1 · FR house wire 2.5 sq mm

Copper conductor runs through the extruder, cooling trough, laser diameter gauge and spark tester. Inject a fault and watch what the gauges see: diameter drifting out of spec, the conductor going off-centre, the spark tester firing.

Outer diameter, last 60 seconds · spec 3.05 to 3.35 mm

Inject a fault:

Events

Simulated line; values are illustrative.

02 · Auto Pareto

Which defects cost the most?

Thirty days of rejections ranked by rupees, metres or count. The bars left of the 80% line are where most of the money goes. Click a defect to analyse it.

DefectCountMetres₹ scrap

Synthetic rejection log, September 2026, lines EXT-1, EXT-2, EXT-3 and SHE-1. Scrap valued at product cost per metre.

03 · Evidence-scored fishbone

Which causes does the data support?

Every cause on the fishbone is tested against 360 production runs. The bar shows how much more often the defect occurs when the cause is present. Click a cause for the evidence and the 5 Whys.

Strong evidence (3× or more)Some evidenceNot supported by data

Evidence

5 Whys

    04 · 8D report

    From analysis to the customer's 8D

    The eight disciplines filled from the data: problem, containment, root cause with evidence, corrective and preventive actions. Add your own notes and GenAI rewrites it; or upload a defect photo to classify it.

    Templates

    8D

    Shop-floor notes (optional)

    Classify a defect photo

    The assistant drafts; the quality engineer confirms the root cause and signs the 8D.

    Impact Dashboard

    A process that stays in control

    With moisture checked at the hopper, die changes on hours and speed ramps capped, insulation thickness now varies far less and stays well inside the limits.

    Insulation thickness, daily average

    Control chart (X-bar) with control limits and minimum spec

    Daily averageOut of controlControl limitsMinimum spec

    Process capability by product

    Capability curves against spec limits, with Cpk

    Figures indicative; validated metrics available on request.

    Before vs After

    How quality problems get solved now

    DimensionBeforeAfter
    Choosing the problemWhatever failed lastPareto by rupees and metres
    DataRegisters, logbooks, sheetsRejections joined with line data per run
    FishboneBrainstormed in a meetingEvery cause scored against evidence
    Root causeOpinion of the senior personData, then 5 Whys, then verified on the chart
    8D reportAbout three weeksDrafted the same day, closed in about three
    PreventionRepeat defectsControl plan and PFMEA updated on closure
    Tools & Tech Used

    The quality analytics stack

    Python joining rejections with line data Line PLC and gauge data speed, temperatures, diameter OpenAI GPT 8D drafting and photo classification D3 Pareto, fishbone and control charts Power BI daily quality huddle SharePoint 8D and CAPA register
    Key Takeaways

    What any plant can borrow

    01

    Rank by rupees, not by noise

    The Pareto in money terms tells the team which single defect to fix first.

    02

    Make every cause testable

    A fishbone cause that can't be checked against data is an opinion. Write each one as a test.

    03

    Close the loop on the control chart

    A root cause is confirmed only when the chart shows the process staying in control afterwards.